1. Home
  2. Vulnerabilities
  3. CVE-2022-50377
0.0
NA
CVE-2022-50377
ext4: check and assert if marking an no_delete evicting inode dirty
Description

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

INFO

Published Date :

Sept. 18, 2025, 2:15 p.m.

Last Modified :

Sept. 19, 2025, 4:15 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2022-50377 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Apply kernel updates to prevent race conditions during inode eviction and dirtying.
  • Update the Linux kernel to the latest stable version.
  • Apply the specific patch for ext4 inode handling.
  • Reboot the system after applying updates.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2022-50377 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2022-50377 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Rejected by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Sep. 19, 2025

    Action Type Old Value New Value
  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Sep. 19, 2025

    Action Type Old Value New Value
    Changed Description In the Linux kernel, the following vulnerability has been resolved: ext4: check and assert if marking an no_delete evicting inode dirty In ext4_evict_inode(), if we evicting an inode in the 'no_delete' path, it cannot be raced by another mark_inode_dirty(). If it happens, someone else may accidentally dirty it without holding inode refcount and probably cause use-after-free issues in the writeback procedure. It's indiscoverable and hard to debug, so add an WARN_ON_ONCE() to check and detect this issue in advance. Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
    Removed Reference kernel.org: https://git.kernel.org/stable/c/0c026f975d24701766cf4ac63995ead9f6d57a59
    Removed Reference kernel.org: https://git.kernel.org/stable/c/318cdc822c63b6e2befcfdc2088378ae6fa18def
    Removed Reference kernel.org: https://git.kernel.org/stable/c/9020f56a3cad1c97b81c7dab2aa67027b59c8f73
    Removed Reference kernel.org: https://git.kernel.org/stable/c/91009e361e8cb2cbd1dc9496cb5fb4f8de3f4b11
    Removed Reference kernel.org: https://git.kernel.org/stable/c/f1ec687ebd1bf146333955b7e209d21508c3ba9f
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Sep. 18, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: ext4: check and assert if marking an no_delete evicting inode dirty In ext4_evict_inode(), if we evicting an inode in the 'no_delete' path, it cannot be raced by another mark_inode_dirty(). If it happens, someone else may accidentally dirty it without holding inode refcount and probably cause use-after-free issues in the writeback procedure. It's indiscoverable and hard to debug, so add an WARN_ON_ONCE() to check and detect this issue in advance.
    Added Reference https://git.kernel.org/stable/c/0c026f975d24701766cf4ac63995ead9f6d57a59
    Added Reference https://git.kernel.org/stable/c/318cdc822c63b6e2befcfdc2088378ae6fa18def
    Added Reference https://git.kernel.org/stable/c/9020f56a3cad1c97b81c7dab2aa67027b59c8f73
    Added Reference https://git.kernel.org/stable/c/91009e361e8cb2cbd1dc9496cb5fb4f8de3f4b11
    Added Reference https://git.kernel.org/stable/c/f1ec687ebd1bf146333955b7e209d21508c3ba9f
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.